Create a port over which SAP and your translator will exchange documents (see the translator page for more information on ports)
VOE4
Translate external partner numbers to internal partner numbers on a sold-to partner basis. The input to this table is the sold-to partner number (E1EDKA1-AG.PARTN), partner type E1EDKA1.PARVW, and external partner number E1EDKA1.PARTN. Note: If you will provide the SAP partner number on E1EDKA1.PARTN, there's no need to populate this table.
External
Some work will also be required on your translator's system to either:
1. Implement a schedule for your translator to pick-up and drop-off documents at the port (if remote triggering will not be used and the port is of type FILE or XML)
2. Setup a script to initiate translation when invoked by SAP via RFC (if remote triggering will be used and the port is of type FILE or XML)
3. Some configuration to configure the tool for ALE (if ALE tRFCs will be used to communicate)
Determine which IDoc type you'll feed to this function module
External
Within your translator, work will be needed to:
1. Define the structure of the IDoc selected
2. Define mappings to translate business partner documents to this structure. If you find gaps where SAP does not provide the needed fields or functionality, you will need to extend SAP's standard offering.
Define your business partners, which transactions you will receive from them, and whom SAP should handle problems when they occur.
VOE2
Define the sales areas (sales org, distribution channel, division) for inbound orders for each sold-to -- the real sold-to (i.e., from EDPAR), not the WE20 customer. This table is consulted if sales area information is not provided in the IDoc's E1EDK14 segments. However, if you specify a sales document type here, it will override any sales order type you specify on the IDoc's K01 segment.
Inbound Setup Procedure